Here you can search through the pages of this Namespace, their attachments and the files uploaded to the system.
Note: the results will only display the items you have permissions to read.
A Spark Order is a multiple-component (batch) order that consists of a Trigger order and contingent Related orders. When a Spark order is submitted, the trigger order is sent to the market while the Related orders are suspended (held). When the trigger component is traded, the Related components are all activated and sent to the exchange to work independently of each other. The Spark's [...]
Order State and Execution The Execution Report message (MsgType=8) is used by the T4 FIX API to electronically notify execution events and order state changes. The following areas are covered by the T4 FIX API Execution Reports: * Confirm the receipt of an order. * Confirm changes to an existing order [...]
An AutoOCO (Automatic One Cancels Other) consists of three components: a Trigger order and the two components of a traditional OCO Order . When the Trigger order is filled, the OCO order (consisting of a Limit order and a Stop order) is activated and consequently submitted to the exchange. An AutoOCO Order is submitted with the New Order List (Tag 35=E) message. [...]
This document outlines how to use the T4 FIX API 4.0 of Cunningham Trading Systems (CTS). The T4 FIX API conforms to the Financial Information eXchange (FIX) Protocol with minor improvements and customizations as presented herein. T4 FIX API applications cannot be run simultaneously with our frontend or other [...]
If at anytime you require assistance from CTS you must send in your FIX messages to API@ctsfutures.com . Our API support will not answer if the messages aren't delimited in a reasonable way for readability Session Initiation After a successful SSL connection, the T4 FIX API basic requirement is to have both the Initiator and Acceptor start with sequence number 1. The client will initiate the FIX [...]
Submitting New Orders The New Order Single message (MsgType=D) is used by the T4 FIX API to electronically submit orders to an exchange for execution. This message is used for all strategy types including outright futures, futures options, spreads and multileg strategies. The instrument for which the order is submitted is identified with the following tags: Tag 48 (SecurityID), Tag 55 (Symbol), Tag 207 (SecurityExchange) and Tag 167 (SecurityType). [...]
Submitting Orders with Multiple Components: Batch Orders The New Order List message (MsgType=E) is used by the T4 FIX API to electronically submit (multiple-component) orders to an exchange for execution. Orders with multiple components are also known as Batch Orders. They are identified by its Contingency Type (Tag 1385). Batch orders can only contain (constituent) orders. The New Order List is built by specifying its ContingencyType (Tag 1385), target [...]
Multiple Traders Under an established FIX Session, multiple traders/users can be authenticated with the Trader Logon message. Trader Logons allow order routing for multiple traders under the same physical connection of the FIX Session. Trader Logons must follow the successful FIX Logon of the initial Master User. To enter Multi-Trader mode, the Master User must explicitly request it as an option on the FIX Logon with Tag 372 (RefMsgTypes) = UCG. [...]
Subscribing to Streaming Data The T4 FIX API provides (optional) subscriptions to streaming market data for all markets available in order routing. Market data is made available asynchronously and concurrently to order routing flow. The market data subscriptions are active during a FIX Session. They are initiated by Market Data Request messages (Tag 35=V). A Market Data Request is a general request for streaming of market [...]
Amending Working Orders The Order Cancel-Replace Request message (MsgType=G) is used by the T4 FIX API to electronically amend (i.e. revise) the replaceable fields of working orders. This message is used for all CTS strategy types including outright futures, futures options, spreads and multileg strategies. The instrument (for which the replace applies) is identified with the following tags: Tag 48 (SecurityID), Tag 55 (Symbol) Tag 207 (SecurityExchange) and Tag 167 (SecurityType). [...]
Application Management Beyond order routing, the T4 FIX API provides additional functionalities to query and manage positions, orders and accounts. The Collateral Inquiry message (MsgTyp=BB) is the cornerstone of (non-routing) application management. If the requests are successful, Collateral Inquiries result in responses from the T4 FIX API server with Execution Reports , Collateral Reports [...]
An AutoOCOM (Automatic One Cancels Other with Multiple Exits ) order consists of three or more components: a Trigger order and multiple components of a traditional OCO Order . When the Trigger order is being filled, multiple OCO orders (consisting of Limit and Stop orders) are activated as the trigger traded volume advances towards the quantity requested for the trigger order. Activation of an OCO component requires passing Risk Assessment, submitting [...]
Logon Traders Under an established FIX Session, multiple traders/users can be authenticated with the Trader Logon message. Trader Logons allow order routing for multiple traders under the the same physical connection of the FIX Session. Trader Logons must follow the successful FIX Logon of the initial Master User.
The FIX API responds to Trader Logons with the Trader Logon Response message. With this message, the [...]
Logging out Traders Under an established FIX Session, multiple traders/users can be authenticated with the Trader Logon message. Trader Logons allow order routing for multiple traders under the the same physical connection of the FIX Session. Trader Logons must follow the successful FIX Logon of the initial Master User. A trader that has been successfully authenticated with a Trader Logon can be logged out by the Master User with a Trader Logout message. The FIX [...]
Logging out Traders Under an established FIX Session, multiple traders/users can be authenticated with the Trader Logon message. Trader Logons allow order routing for multiple traders under the the same physical connection of the FIX Session. Trader Logons must follow the successful FIX Logon of the initial Master User. A trader that has been successfully authenticated with a Trader Logon can be logged out by the Master User with the Trader Logout message. Identifying the [...]
A Flatten order can be used to flatten a current position regardless of what that position is. The T4 FIX API server figures out the volume and Buy/Sell parameters. If a position does not currently exist for the SecurityID (Tag 48) of the submitted flatten order, the order is rejected. A Flatten Order is entered with the New Order Single (Tag 35=D) message. Following [...]
Requesting the Status of an Order The Order Status Request message (MsgType=H) is used by FIX API clients to electronically interrogate the instantaneous state of an order. The OrderId Tag (37) identifies the specific order for which the Order Status Request is submitted. To pinpoint the order's instrument, the SecurityID (Tag 48) and Side (Tag 54) must also be specified. [...]
A Queue Order submits an order to the T4 FIX API server for queueing (i.e. risk assessed, suspended and waiting for a request to activate). A Queue Order (Tag 10102=6) is queued with the New Order Single (Tag 35=D) message with an Activation Value of 0 (Tag 10103=0). Subsequently, a Queued Order is activated (to submit to the exchange) with the Cancel Replace Request [...]
At Time Activation Orders will be held (i.e. suspended) in the T4 FIX API server until the specific time (as entered with the Activation Value - Tag 10103) occurs. At this activation point, the order is released to the exchange. An Activation Order is entered with the New Order Single (Tag 35=D) message. Following are the most relevant tags to build an At Time Activation Order.
Tag 10102=5 [...]
An OCO (One Cancels Other or Order Cancels Order) consists of a buy limit order below the market and a buy stop order above the market, or a sell limit order above the market and a sell stop order below the market. When one gets filled the other is cancelled. If one is partially filled then the volume on the other is reduced accordingly. An OCO Order is submitted with the New Order [...]
Rejecting Attempts to Amend or Cancel Orders The Order Cancel Reject message (MsgType=9) is used by the T4 FIX API to electronically reject (failed) attempts to cancel or replace an order. Cancel Rejects are only generated for unsuccessful client side Order Cancel Request , Order Cancel Request or List Cancel Request messages. Unsolicited Cancel Rejects may also be generated for cancel [...]
Canceling Working Orders The Order Cancel Request message (MsgType=F) is used by the T4 FIX API to electronically cancel (i.e. pull) working orders. This message is used for all CTS strategy types including outright futures, futures options, spreads and multileg strategies. The instrument for which the cancel-request is submitted is identified with the following tags: Tag 48 (SecurityID), Tag 55 (Symbol) and Tag 207 (SecurityExchange). In addition to full market specification, [...]
On Price Activation Orders will be held (i.e. suspended) in the T4 FIX API server until the market trades at or below (or at or above) the activation price (as entered with the Activation Value - Tag 10103). At this activation point, the order is released to the exchange. An Activation Order is entered with the New Order Single (Tag 35=D) message. Following are the most relevant tags to build an On Price Activation Order. [...]
The T4 FIX API conforms to the Financial Information eXchange (FIX) Protocol with minor improvements and customizations. Documentation on FIX can be found at http://www.fixprotocol.org .
Requirements
To develop to the T4 FIX API, you need a dedicated SSL connection to a T4 FIX API [...]
Order Mass Status Request The Order Mass Status Request message (MsgType=AF) is used by the T4 FIX API to list open orders. Requests can be submitted for a specific Account (Tag 1), UserName (Tag 553), SecurityID (Tag 48), Symbol (Tag 55) and Security Exchange (Tag 207). Orders can also be filtered by Time-In-Force (Tag 59). UserName filtering (Tag 553) is only available under the Multi-Trader mode (Tag 372=UCG) of the Logon message. The Order [...]
A MarketIfTouched (MIT) Order is submitted to T4 FIX API server to suspend and await subsequent exchange submittal when a trigger price is hit. Once a trade occurs at the trigger price, the T4 FIX API server releases (to the exchange) the MarketIfTouched Order as a Market Order (Tag 40=0). A MarketIfTouched Order [...]
Message Rejection FIX Session rule violations are manifested through the Reject message. The receipt of a Reject message signals a serious violation of FIX Session rules. Appropriate action must immediately be taken by the receiver of a Reject message. A rejected message may be retransmitted by the sending application if a correction is appropriate. The T4 FIX API can detect an extensive set of FIX session violations and [...]
On Market Mode Activation Orders will be held (i.e. suspended) in the T4 FIX API server until the specific market mode event (as entered with the Activation Value - Tag 10103) occurs. At this activation point, the order is released to the exchange. An Activation Order is entered with the New Order Single (Tag 35=D) message. Following are the most relevant tags to build an On Market Mode Activation Order. [...]
[...] Canceling Orders with Multiple Components The List Cancel Request message (MsgType=K) is used by the T4 FIX API to electronically cancel (i.e. pull) all components of contingent (Batch) orders (e.g. OCO, AutoOCO, Spark). The constituent order components must be in the working or suspended (held) state to result in a successful cancellation. This message is used for all CTS strategy types including outright futures, futures options, spreads and multileg [...]
[...] Requests To receive Security Definitions as responses to Security Definition Requests, the initiating FIX session Logon message must have Tag 372 (RefMsgType) set to "c" (i.e. Enable security definitions requests). Security definition requests that are not enabled will be rejected with a Security Definition containing a SecurityResponseType of Reject Security Proposal (Tag 323=5).
Definition of Securities The T4 FIX API provides a mechanism to list the securities available for [...]